Viewing a device's actions

On the Actions page, you can view the actions that have been requested on the device. You can select an action, and view information about the action request it belongs to.

To view a timeline of an action's status changes, see the device's History page.

To view a device's Actions page, your role needs to be granted the View permission for one of the supported actions. To view a particular action on the Actions page, your role needs to be granted the View permission for that action.

If your user role is assigned to select device groups, you can only see the devices that belong to your assigned device groups.

To view action information for a device:

  1. On any page that shows linked device identifiers in the first column of the results grid, such as the All Devices page in the Devices area, click the link for the device you want to view. Summary information about the device shows in the page header.
  2. Click Actions.

A new page opens to show the device's actions.

The Actions page includes a default collection of action information organized in the following columns:

Column Description
Request The request name and request ID
Action > Status

The progress of the action on the device and the date of the last status update (as a relative date, such as 23 days ago)

Hover over the relative date to view the exact date and time in a tooltip.

Action status can be one of the following:

  • Failed: either the system or the device is unable to perform the action, the request was declined, or the request was auto declined

    Add the Action > Status details column to see the reason for the failure.

  • Pending: the action hasn't been downloaded to the device or the request requires approval
  • Ready (Send Message and Scheduled Freeze requests only): the action has been downloaded to the device, but is scheduled to take place in the future
  • Canceled: a user has canceled the action
  • Processing: the action is currently being performed on the device but the action hasn't yet been completed

  • Succeeded: the action has run on the device and the action was completed successfully

    • Cryptographic Wipe
    • Run Script

  • Completed: the action has run on the device

    • Delete File

      For Delete File requests, review the Output column, the Log file, or Events to determine if the action was successful.

      When a Delete File request runs on a device, the files found and the files deleted may not be the same. The Output column and Events show the number of files found and the number of files deleted. The Log file contains further details about which files were found and which files were deleted, as well as the reason files weren't deleted.

    • Freeze

      For Firmware Freeze requests, review the Action > Status details column to determine if the action was successful at both the OS and firmware levels.

      A Firmware Freeze request that couldn't be processed may temporarily show an action status of Completed before the status is updated to Failed.

    • Remove Freeze
    • Run Playbook
    • Send Message
    • Unenroll
Type

The type of request the action belongs to
Output

The output, if any, of the action

  • Cryptographic Wipe: a link to download the Certificate of Sanitization

  • Delete File - Delete Files: Found n – Deleted m

    The number of files found on the device (n) and the number of files deleted (m)

    If the number of files found is different than the number of files deleted, see the log file for detailed information.

    Click Log file to download the log file.

  • Delete File - Delete All Files: a link to download the Certificate of Sanitization and the log file

    Click Certificate to download the Certificate of Sanitization.

    Click Log file to download the log file.

  • Freeze: the masked unfreeze code A 4 to 8 digit passcode that a user can enter on a frozen device to unfreeze it.

    For security reasons, the unfreeze code is masked. To show it, click (Show). An Unfreeze code unmasked event is logged to Event History. To hide it again, click (Hide).

  • Run Script: the script return code used to inform the user whether the request was successfully run

    The script returns 0 if the script is a success. The other return codes are defined in the script.

  • Send Message: the message response

    A semi-colon (;) delimited list of Field Names and values for the Custom Device Fields included in the response to the message

    Format: Field Name 1: value 1; Field Name 2; value 2

    Shows No Data when:

    • The message requires a user response but a response hasn't been received
    • The message was informative and Custom Device Fields were only used to share information or weren't used at all

    Hover over the field to see a tooltip to see all values or click in the row to see a request overview.
Requester The full name and email address of the user that created the request
Created date The date and time the action was created
Action > Status updated The date and time the status was last updated

By default, the following permanent filters are used to generate the Actions page:

You can also click to add additional filters.

You can't filter using the Output column. You can add the Message name and Script name columns and add them as filters.

To view information about the request an action belongs to, click anywhere in the action background. The request overview opens to the right of the work area. The following information is available:

The header shows the default or user-defined name of the request.

Each request contains a collapsible Overview and Configuration section.

The overview section for each request contains the Request ID, which is the system-defined identifier of the request

The following tables show the additional information that may be included in the overview and configuration sections depending on the options selected in the request:

Cryptographic Wipe Overview and Configuration details
Item Description
Overview
Description

User-defined description of the request (if it was added when the request was created)
Wipe type

The data sanitization process used

  • Cryptographic erase
Result

A link to the Certificate of Sanitization

Click Certificate to download the certificate.
Configuration
Unenroll devices and free licenses

Shows if the Cryptographic Wipe request was set to unenroll Windows devices on completion
Delete File Overview and Configuration details
Item Description
Overview
Description

User-defined description of the request (if it was added when the request was created)
File name, folder and path

Only applies to Delete File requests

The files and folders entered in the Delete Files request
Result

Found n – Deleted m: the number of files found on the device (n) and the number of files deleted (m)

If the number of files found is different than the number of files deleted, see the log file for detailed information.

(Delete All Files) Click Certificate to download the Certificate of Sanitization.

Click Log file to download the log file.

File Date Attributes are not included in the log file for Delete All Files.
Configuration
Overwrite the data x times The number of times the data was overwritten
Include File Date Attributes in the log file

Only applies to Delete File requests

An indication of whether Include File Date Attributes in the log file was selected in the Delete Files request
Disable the Windows OS

Only applies to Delete All Files requests

An indication of whether Disable the Windows OS was selected in the Delete All Files request
Unenroll devices after the File Delete is complete

Only applies to Delete All Files requests

An indication of whether Unenroll devices after the Wipe is complete was selected in the Delete All Files request
Freeze Overview and Configuration details
Item Description
Overview
Description

User-defined description of the request (if it was added when the request was created)
Freeze type

The type of Freeze

  • On-demand: Freeze the device as soon as possible
  • Scheduled: Freeze scheduled for a future date and time
Scheduled date

The date and time the device is scheduled to be frozen

Only shows when On or after a certain date was selected in the Freeze request
Unfreeze code

The code that's entered directly on each frozen device to unfreeze it and make the device operational again

For security reasons, the unfreeze code is masked. To show it, click (Show). An Unfreeze code unmasked event is logged to Event History. To hide it again, click (Hide).
Configuration
Message

The name of the Freeze message and a preview of the message the users see on their device when it's frozen

Click (Show message) to open a larger message preview.
Send status updates Status updates trigger an email notification for this request
Events

The events that trigger an email notification

Only shows if Send status updates was selected in the request
Send email

The email addresses that receive the notification

Only shows if Send status updates was selected in the request
Remove Freeze Overview and Configuration details
Item Description
Overview
Description

User-defined description of the request (if it was added when the request was created)
Configuration
Unfreeze devices and cancel pending on-demand freeze requests

Indicates that the Remove Freeze request:

  • Unfreezes devices with a Device Freeze Status set to Frozen or Frozen - Timer Expired

  • Removes newly submitted On-demand Freeze requests with an Action Status of Pending
Cancel pending and downloaded freeze requests scheduled for a future date Indicates that the Remove Freeze request cancels Scheduled Freeze requests with a status of Pending or Ready
Send status updates Indicates that status updates trigger an email notification for this request
Events

The events that trigger an email notification

Only shows if Send status updates was selected in the request
Send email

The email addresses that receive the notification

Only shows if Send status updates was selected in the request
Run Playbook Overview and Configuration details
Item Description
Overview
Name

The system-defined name of the request

Click (Show playbook) to view the type of playbook and its configurations
Configuration

If a variable was used in a configuration in the request, it is displayed as such in this area.
Recovery > BitLocker Recovery key The device's BitLocker recovery key
File operations (add or delete) playbook

Delete file > Path and file name to delete

 The file path of the file requested to delete

Add file > File path

 The location on the device where the file is stored

Add file > Host file URL

 The URL where the file was downloaded from
Set/remove registry keys playbook

Set registry key > Registry name, value, and path

 Details about the registry key that was added, or the registry key value that was updated

Remove registry key > Registry name, value, and path

 Details about the registry key value that was removed
Restore from image playbook

Restore > Manifest file URL

 The URL where the manifest file was stored

Restore > Username

 The username used to access the server

Restore > Credentials

 The password or key associated with the username
Run script playbook

Batch script

 Click to view the script content
Run Script Overview details
Item Description
Overview
Description

User-defined description of the request (if it was added when the request was created)
Script name

The name of the script

Click (Show script) to open a preview of the script. The preview contains the following information:

If the request was run on Windows and Mac devices, the script contains both a PowerShell Script and Bash Script tab.
Return code For actions with an action status of Completed, the return code from the script

There is currently no configuration section for Run Script.

Send Message Overview and Configuration details
Item Description
Overview
Description

User-defined description of the request (if it was added when the request was created)
Message response

The message response

A semi-colon (;) delimited list of Field Names and values for the Custom Device Fields included in the response to the message

Format: Field Name 1: value 1; Field Name 2: value 2

Shows No Data when:

  • The message requires a user response but a response hasn't been received
  • The message was informative and Custom Device Fields were only used to share information or weren't used at all
Configuration
Scheduled date

The date and time the message is scheduled for

Only shows when On or after a certain date was selected in the Send Message request
Message

The name of the End User Message and a preview of the message

Click (Show message) to open a larger message preview.

The name of the End User Message wasn't recorded prior to Secure Endpoint 9.0 (April 2024). Requests created prior to Secure Endpoint 9.0 show No data as the message name but still contain a preview of the message.
Display

How the message is displayed

  • Pop-up notification
  • Full screen
Frequency The number of times a participant is allowed to snooze the message
Unenroll Overview and Configuration details
Item Description
Overview
Description

User-defined description of the request (if it was added when the request was created)
Configuration
Exclude missing devices Exclude missing devices was selected in the Unenroll request

While you are viewing a page or report, its data is not updated dynamically as new data becomes available. To show the most recent data available in the system, such as information that was just uploaded from a device, click the icon in the bottom left of the page. The Last updated field updates to the current date and time.

You can click (Save as report) on the action toolbar to save the page as a new report. You can access your report in the My Reports view of the Reports page. Any filter, column, and sort customizations that you added to the page are saved to the new report.

To identify the device in this report, the Device column is automatically included.

You can click (Export) to export the page as a report and download it to your computer. If you've edited the page's filters or added or removed columns, your changes are reflected in the exported report.

When you export the information from Actions:

  • Device name is exported as the following columns: Identifier, Device name, and Serial number.
  • Request is exported as a Request name column and a Request ID column.
  • Output is exported as the following columns: Unfreeze code, Result, Message response, and Script return code.
  • Requester is exported as a Requester name column and a Requester email column.

To identify the device in the exported report, the Device, Username, and OS name columns are automatically included.